Harden production reliability and release readiness - #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root causes addressed
The review found several production risks around bounded waits, arithmetic overflow, non-atomic metadata updates, PID reuse, symlink handling, mapping lifetime leaks, unsafe publication ordering, and recovery from interrupted writes. These changes resolve those failure modes and add regression tests around the affected contracts.
Validation
Release follow-up
GitHub private vulnerability reporting is currently disabled for this repository. The package code and validation gates are green, but that repository security setting should be enabled before publication; the release documentation records this requirement.